Scalability of providing packet flow management

ABSTRACT

Systems and methods for managing packet flows in a communication network are provided. Packet information can be cached on different levels and used to avoid external queries. The cache information can also be correlated with other types of information, such as location information, to be able to serve that information quicker than if one or more external queries were to be made. A demux manager can provide routing and session setup, by routing packets that already have a session to the session manager and assigning packets to a session manager if they are not already assigned to a session. The tiered architecture also provides scalability to many users and minimizes delays even during high call volumes because the load can be distributed well across the gateway&#39;s resources.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.11/952,980, entitled “Scalability of Providing Packet Flow Management,”filed Dec. 7, 2007 which claims benefit under 35 U.S.C. §119(e) of U.S.Provisional Patent Application No. 60/873,493, entitled “Apparatus andMethod for Providing a Call Session Control Function,” filed Dec. 7,2006, the contents of both of which are hereby incorporated by referenceherein in their entirety.

FIELD OF THE DISCLOSURE

This disclosure relates to a system and method for providing packet flowmanagement in a communication network.

BACKGROUND

Wireless communication systems and networks are used in connection withmany applications, including, for example, satellite communicationssystems, portable digital assistants (PDAs), laptop computers, andcellular telephones. One significant benefit that users of suchapplications obtain is the ability to connect to a network (e.g., theInternet) as long as the user is within range of such a wirelesscommunication system.

Current wireless communication systems use either, or a combination of,circuit switching and packet switching in order to provide mobile dataservices to a mobile node. A mobile node can be a cell phone, a PDA, aBlackberry, a laptop computer with a wireless card, or any otherwireless device. Generally speaking, with circuit-based approaches,wireless data is carried by a dedicated (and uninterrupted) connectionbetween the sender and recipient of data using a physical switchingpath. Once the direct connection is setup, it is maintained for as longas the sender and receiver have data to exchange. The establishment ofsuch a direct and dedicated switching path results in a fixed share ofnetwork resources being tied up until the connection is closed. When thephysical connection between the sender and the receiver is no longerdesired, it is torn-down and the network resources are allocated toother users as necessary.

Packet-based approaches, on the other hand, do not permanently assigntransmission resources to a given call, and do not require the setup andteardown of physical connections between a sender and receiver of data.In general, a data flow in packet-based approaches is “packetized,”where the data is divided into separate segments of information, andeach segment receives “header” information that may provide, forexample, source information, destination information, informationregarding the number of bits in the packet, priority information, andsecurity information. The packets are then routed to a destinationindependently based on the header information. The packet flow mayinclude a number of packets or a single packet. Services may be appliedto a packet flow such as lawful interception (wire tapping), VirtualPrivate Networks (VPNs), and firewalls.

A part of the evolution of packet based communications has been thedevelopment of IP Multimedia Subsystem (IMS). IMS is an architecturalframework for delivering internet protocol (IP) multimedia to mobilenodes. A call session control function (CSCF) can manage much of thesignaling that occurs in an IMS core. The CSCF functionality can belogically divided into three functionalities: a Proxy-CSCF (P-CSCF), anInterrogating CSCF (I-CSCF), and a Serving CSCF (S-CSCF). Additionally,the CSCF functionality is envisioned by two different groups forinclusion in two different topologies: Global System for MobileCommunications (GSM) and CDMA 2000. The 3^(rd) Generation PartnershipProject (3GPP) is responsible for IMS which works with GSM systems andthe 3^(rd) Generation Partnership Project 2 (3GPP2) is responsible forMultimedia Domain (MMD) which is used with CDMA systems and is based onthe 3GPP IMS concept. With both IMS and MMD, several different functionsare described and problems can arise if packet flows are not managedamong the functions.

SUMMARY OF THE DISCLOSURE

Systems and methods for providing packet flow management in acommunication network are disclosed. In some embodiments, a gateway in acommunication network includes a demux manager residing in the gatewaythat processes one or more incoming packets, caches information relatingto new process instance assignments, and allocates a process instance toa new packet flow, a process instance that caches information relatingto sessions the process instance is handling in a computer readablemedium in the gateway, and a network processing unit flow residing inthe gateway that is setup by the process instance to route incomingpackets that match specified information to a corresponding processinstance.

In certain embodiments, a method of processing packets includesreceiving a packet at a gateway, determining if the packet matches alimited set of criteria, and if there is a match forwarding the packetto a corresponding process instance, otherwise forwarding to a demuxmanager, analyzing the packet at the demux manager to determine whetherto assign a new process instance to handle a new packet flow anddetermining how to route the packet, and receiving a new packet at aprocess instance that is assigned from the demux manager and creating acache entry with information from the new packet.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating an IP multimedia subsystem (IMS)architecture in accordance with certain embodiments;

FIG. 2 is a block diagram illustrating a multimedia domain (MMD)architecture in accordance with certain embodiments;

FIG. 3 is a block diagram of components of a gateway for managing packetflows in accordance with certain embodiments;

FIG. 4 is a block diagram of flows through a gateway and among functionsin accordance with certain embodiments;

FIG. 5 is a block diagram of an implementation of components within agateway in accordance with certain embodiments; and

FIG. 6 is a flow diagram of a process of providing packet flowmanagement in accordance with certain embodiments.

DETAILED DESCRIPTION

Systems are methods for providing management of packet-based flows on acommunication network are disclosed in some embodiments. A gateway maybe used to implement the management of packet flows for IP multimediasubsystem (IMS) and multimedia domain (MMD) architectures. Directingpacket flows and providing physical mapping of IMS and MMD functions canbe provided by a combination of hardware and software. Residing withinthe gateway can be one or more network processing units, line cards, aswell as packet and voice processing cards. Software modules such as anetwork processing unit (NPU) flow, a demux manager, a session manager,and a registrar can provide physical mapping and packet flow directionamong the many functions. The software modules can also be setup toprovide the physical mapping and packet flow direction in a scalablefashion, so heavy call volumes can be distributed to minimizecall/session setup delays in some embodiments.

FIG. 1 illustrates an IP multimedia subsystem (IMS) where logicalcomponents of a network setup are shown in accordance with someembodiments. FIG. 1 includes a P-CSCF 110, an I-CSCF 112, a S-CSCF 114,a Home Subscriber Server (HSS) 116, a Subscriber Location Function (SLF)118, User Equipment (UE) 120, Breakout Gateway Control Function (BGCF)122, Media Gateway Control Function (MGCF) 124, Media Gateway (MGW) 126,Public Switched Telephone Network (PSTN) 128, Multimedia ResourceController (MRFC) 130, and Multimedia Resource Function Processor (MRFP)132. HSS 116 is a master user database that supports the S-CSCF or othernetwork entities that handle calls and sessions. HSS 116 storessubscription-related information such as user profiles, performs userauthentication and authorization, and can provide information about thephysical location of the user. When multiple HSSs are used in a networka SLF 118 can be used to direct the queries to HSS 116 storing theinformation. Legacy signaling networks may also use the HSS forservices. MRFC 130 communicates with S-CSCF 114 and controls the MRFP132 to implement media related functions. The combination of MRFC 130and MRFP 132 provides a source of media in the home network. BGCF 122 isa server that can route based on telephone number and is used whencalling to a phone on the circuit switched network. MGCF 124 and MGW 126are used to convert signaling from IMS to that which is appropriate forPSTN 128 circuit switched networks. The IP Multimedia Networks caninclude application servers and other network entities that provideservices to user equipment (or mobile node) 120. The user equipment (ormobile node) can include a cell phone, a personal digital assistant(PDA), or a laptop computer.

FIG. 2 illustrates a Multimedia Domain (MMD) system 210 within a largernetwork. The MMD system 210 includes many of the same functions as theIMS system of FIG. 1, but further includes an access gateway/foreignagent 212 to communicate with access networks 214, as well as a homeagent 216 to provide Mobile IP support to mobile stations 218 (or mobilenode). A policy decision function (PDF), which can be included in a IMSor MMD network stores policies governing a user's session. Applicationservers such as an open systems architecture (OSA) application server222 and SIP application server 224 provide applications such as locationbased services, video, email, chat, gaming, and other data andmultimedia content.

As shown in FIGS. 1 and 2 a number of functions can be included in IMSand MMD networks. Several of these functions are used in providing, forexample, voice over IP (VoIP) routing and enhanced services, such asenhanced charging, stateful firewalls, traffic performance optimization(TPO). In some embodiments, one or more of these functions can beprovided by a single entity in the network such as a gateway. Thephysical mapping of these function to entities in the network, can beperformed to minimize session setup delay and ease management ofphysical entities even as the number of sessions increases. As thenumber of sessions increases, the load may need to be distributed amongone or more entities that perform the same task, entities which can beeither logical and internal to the gateway or physical.

FIG. 3 illustrates a control plane architecture for a gateway inaccordance with certain embodiments. A session manager 310 services andprocesses user session data flow for user equipment/mobile subscribers.Session manager 310, which is the same session manager as describedabove, includes functional layers such as a system service layer 312, acall processing layer 314, and a call processing support services layer316. The system services layer 312 provides an interface forinstructions to be passed to the session manager and the other layers. Acommand line interface (CLI) 318 as well as network processing unit 320interface are included. The call processing layer 314 includes a servicebroker/Service Control Interaction Manager (SCIM) 322, a CSCF core 324that includes an I-CSCF 326, P-CSCF 328, and S-CSCF 330, a unifiedmessage mapping interface 332, applications 334, and a SIP stack 336.Applications 334 includes registrar function. The registrar functioncaches information relating to the subscriber and the session enablinglookup of information without having to query external databases. Insome embodiments, the CSCF core includes one of the CSCFfunctionalities, for example, the P-CSCF. The call processing supportservices layer 316 includes a variety of services such as routing andaddress translation service 338, subscriber management service 340,changing interface service 342, media interface service 344, QoS policyinterface service 346, security interface 348, and regulatory serverinterface 350.

Looking at the call processing layer 314, this layer includes signalingprotocols and call control using universal SIP as an application programinterface (API). The signaling protocols can be SIP or can be otherprotocols like ISUP, MGCP, or H.323. Further, the call processing layer314 allows interworking between SIP variants and other protocols througha unified mapping interface. The unified mapping interface can convertprotocol specific messages and parameters to a universal SIP like APIformat. SIP like messaging is used, in some embodiments, because SIP hasthe largest message set and can cover the possible messaging scenariosfor SIP and the other protocols. The call processing layer 314 can alsoprovide transparency to data that need not be processed by the CSCF coreby placing that information into an envelope. Parameters that are not ofinterest can be placed in an envelope and remain unmodified. The CSCFcore allows any text string as the calling and called number, and thenumber does not need to be restricted to an E.164 number. The numbercould be, for example, an Address of Record (AoR) or any name stringwith a domain name.

The gateway can implement a number of different approaches for providingscalability and session initiation protocol (SIP) packet flow managementin some embodiments. A port number based routing approach provides asubscriber a port for sending and receiving requests and responses. Theport directs the request and responses to the session manager assignedto the subscriber. A NPU flow can be installed on that port to recognizepacket flows originating from a particular subscriber. In anotherapproach, for example, packets/messages can go through a SIP demuxmanager, and the SIP demux manager can direct the packets/message to theappropriate session manager instance or function. In other embodiments,a NPU flow can be installed for each registered mobile node based themobile node's IP address and port number. The NPU flow can be installedby the registrar function of the session manager in certain embodiments.When a mobile node sends its contact IP address and port number as partof the registration process, the registrar can cache the contactinformation and install the NPU flow for the destination IP address andport number.

A demux manager 352 resides in the signal routing layer 354, as shown inFIG. 3. The signal routing layer 354 with the demux manager candetermine where a packet flow is sent for processing. The packet flowcan be sent to a process instance for further processing and/or signalhandling. The demux manager can be used to analyze packet flows ortraffic entering into a gateway. This analyzing may encompass packetsniffing, extracting of information from packet headers, sortingextracted information, deep packet inspection, and processing ofinformation obtained from one or more packets. Messages analyzed by ademux manager can contain information which can be extracted (orsniffed) such as an IP-address assigned to the mobile node, a networkaccess identifier (NAI), an international mobile subscriber identity(IMSI), a mobile subscriber identification (MSID), a correlation-ID (forCDMA implementations), a user data record (UDR), event data records(EDR), a calling-station-ID, and/or any other applicable information.

The demux manager can also direct packet flows among functions internalto the gateway and physical entities to which other functions aremapped. In directing packet flows, demux manager can steer packet flowsto balance loads. For example, if a packet is to be sent to more thanone function and order does not matter, the demux manager sends thepacket to the least loaded or a less congested function. The demuxmanager, in some embodiments, can determine congestion based onoutstanding packets at different functions or from the delay when one ormore packets return to the demux manager. Information extracted frompackets can be cached locally in the signal routing layer to allowprocessing to occur without retrieving information from externaldatabases.

In certain embodiments, incoming packets are sent to a first in, firstout (FIFO) queue in the demux manager. The packet at the head of thequeue is de-queued and inspected to see how long the packet has beenwaiting in the queue. If the packet has waited longer than a pre-settime, the packet is deemed to be too old and dropped. Otherwise, thepacket is inspected to see if a new session is to be established or ifthe packet is to be routed to a session manager instance or otherfunction. If a new session is to be established, a session managerselection routine is invoked and the packet is forwarded to the selectedsession manager. Packets that belong to an already established sessionare forwarded to the corresponding session manager previously selected.A demux manager can keep a list of the session managers and assign aweighted load factor to each session manager. The list is sorted by theweighted load factor so the least loaded session manager can be selectedfor a new session.

The load factor can be determined by calculating the followingparameters: the number of active sessions, dormant sessions, outstandingrequests, round trip time, and the load on the processing unit where thesession manager is running, in some embodiments. The load factor can becalculated by obtaining a maximum value for each of the parameters anddetermining how each session manager is relative to the maximum. Each ofthe parameters is assigned a percentage with the total adding to 100.The parameters and the list sort order can be periodically updated.Depending on the availability and load levels indicated in the list, newsessions managers can also be added dynamically.

As mentioned above, the demux manager inspects the packets and completesa certain amount of processing, in certain embodiments. The processingcan involve parsing the packet header to extract information in some ofthe fields, with some or all of this information being cached, if theinformation is not stored already. The information can be used to verifythe packet's authenticity (e.g., the packet is not part of some attackon the system) and to validate that the packet is not malformed. Theinformation that can be cached includes Contact (IP address/Fullyqualified domain name of mobile node) and Address of record/Public userId. The packet is then routed to the session manager handling thepacket's session.

Demux manager provides direction handling of packets for a collapsedcall session control function (CSCF), in certain embodiments, which canbe implemented on the gateway and with external CSCF entities. Directionhandling can be implemented based on a rule or rule set in a collapsedCSCF in some embodiments. FIG. 4 illustrates CSCF component interactionin accordance with certain embodiments. FIG. 4 includes a gateway 410, acollapsed P-CSCF 412, a collapsed I-CSCF 414, a collapsed S-CSCF 416, avisited network P-CSCF 418, an I-CSCF 420, a S-CSCF 422, a media gatewaycontrol function (MGCF) 424, and a border gateway control function(BGCF) 426. If a packet is coming from a mobile node (MN) or a visitednetwork P-CSCF 420 then analysis can be performed on originating addressand/or on the destination address. If both the numbers are notregistered within the same network device such as the gateway, then thepackets are proxied to an external entity as described in the routingtable below.

In some embodiments, demux manager sends packet(s) to the sessionmanager instance that can handle the session or that is already handlingthe session. To identify the session manager instance handling thesession, the demux manager determines whether to analyze based on anoriginating subscriber address or a destination subscriber address.Based on the network device or the entity the message is coming from,the demux manager can determine whether to look for a source or adestination address. In some embodiments, some proprietary parameter isinserted into a SIP message to aid the decision without much, if any,additional analysis.

The logic in demux manager to identify the session manager can beimplemented as follows. Check the via/source address. If this addressmatches one of the registered address then the packet is coming from themobile node. Otherwise, if via/source address matches one of the peeringserver addresses, then use that information to make a routing decisionand perform the origination/destination address analysis. Otherwise, ifvia/source address matches one of the cached server's informationreceived from service route/path, use that information to make therouting decision, and add a direction flag in the subscriber table.Otherwise, do the destination address analysis assuming the call (orpackets) is coming from the network and if destination address is alsonot there in the hash table, then allocate to a new session manager.

The table below describes direction handling of incoming packets by ademux manager and/or session manager when the gateway is acting as aP-CSCF only in accordance with certain embodiments. P-CSCF receivesmessages from the following components: one or more mobile nodes, a homenetwork I-CSCF, and a home network S-CSCF.

Incoming Incoming Parameter interface Message Handling Directionanalysis Mobile Register P-CSCF Register comes to the P-CSCF from amobile node. node to adds a Path Demux manager allocates a sessionmanager instance P-CSCF header and passes the register message to thatinstance. I-CSCF/ 200 ok P-CSCF Demux manager checks for the presence ofa service S-CSCF to for stores the route header to identify the functionthat is to be P-CSCF Register service performed. If the service routeheader is present, the route info. message is likely either coming froma S-CSCF or an I-CSCF. Otherwise, the demux manager can perform adestination address analysis to determine direction. MN to Non none If asecurity association is present the request goes to P-CSCF register thesession manager instance handling the session dialog because themessages are sent on the port exchanged creating during securityassociation setup. The session request manager handling the sessionreceives incoming packets on the port exchanged during setup. Whenreceived at the session manager either before or instead of at the demuxmanager, a search similar to the demux manager's search is performed atthe session manager to find the direction. If the source IP address is aregistered subscriber, then the session manager performs P-CSCFfunctionality processing. If a security association is not present,demux manager routes the packet(s) to the session manager instancehandling the session. A proprietary header can be inserted by the demuxmanager to indicate whether the message is for originating subscriber ordestination subscriber so that CSCF core does not have to perform thesame analysis again. Based on the proprietary parameter session managercan be alerted to perform P-CSCF functionality processing. S-CSCF/ Nonnone The path header information is stored by S-CSCF in I-CSCF toregister the session manager instance and can be sent in P-CSCF dialogincoming requests coming from I-CSCF and S-CSCF creating in the routeheader. If this string requests (pcscf_smgr_instance) is present in theusername of the route header, CSCF core performs P-CSCF processing. Alsodemux manager can be alerted to perform analysis on the destinationnumber and send the analysis to the session manager instance where thedestination subscriber is registered.

The table below describes direction handling of incoming packets by ademux manager and/or session manager when receiving messages or packetsfor an I-CSCF. An I-CSCF can receive messages from the followinginterfaces: a home P-CSCF 412, a visited network P-CSCF 418, a homeS-CSCF 422, an external I-CSCF 420, an external S-CSCF 422, and anexternal BGCF 426.

Incoming Incoming Parameter interface Message Handling Directionanalysis Home/visited Register Store If path parameter is present, thepacket is coming from P-CSCF address P-CSCF and the demux managerallocates a session received in manager (if not a re-registration orde-registration) and via as that passes the register message to thesession manager is the instance. P-CSCF CSCF core checks for thepresence of path header. If address. I-CSCF function is configured andthe path header is present in the register message coming from demuxmanager, I-CSCF is the first contact point for the message and performsI-CSCF functionality. Home 200 OK Store Since the service route ispresent demux manager S-CSCF for service knows the direction, and CSCFcore performs I-CSCF Register route function to the packet(s). header.Home/visited Non none Demux manager identifies the session managerP-CSCF register instance by looking at the route header that includesdialog the session manager instance. creating CSCF core checks the via.If the via is one of the request peering servers or a P-CSCF via addressobtained during registration, the CSCF core performs the I-CSCF functionfor originating subscriber. If topology hiding is not required nonregister messages can go directly to the S-CSCF by-passing the I-CSCF.External Non none If the packet(s) are not coming from the P-CSCFnetwork register interface, the packet(s) are bound for a destinationI-CSCF/ dialog subscriber or for proxying to another proxy. DemuxS-CSCF/bgcf creating manager performs a destination address analysis torequest determine the session manager instance handling the session. Ifone is found the packet(s) are routed to that instance. At CSCF core,the packet(s) are checked using the learned P-CSCF address to determineif the packets are coming from the mobile node or a P-CSCF for I-CSCFfunction processing. Otherwise S-CSCF function processing is performed.Home Non none Direction handling is performed by the demux S-CSCFregister manager by looking at the peering server table. dialog creatingrequest

The table below describes direction handling of incoming packets by ademux manager and session manager when receiving messages or packets foran S-CSCF. A S-CSCF receives messages from the following interfaces:P-CSCF 412, visited network P-CSCF 418, I-CSCF 414, MGCF 424, externalI-CSCF 420, external S-CSCF 422, external BGCF 426.

Incoming Incoming Parameter interface Message Handling Directionanalysis Home Register Store path If path parameter is present,packet(s) are coming I-CSCF header from home I-CSCF. The demux managerinfo. Add allocates a session manager (if message is not a servicere-registration or de-registration) and passes the route. associatedregister message packet(s) to the session manager instance. The CSCFcore checks for the presence of a path header to determine that thepacket(s) are coming from the I-CSCF. Home/visited Non none Demuxmanager identifies the session manager P-CSCF register instance handlingthe session by checking the dialog route header that includes thesession manager creating instance. The CSCF core checks the via, and ifrequest the via is one of the peering servers or P-CSCF via addresseslearned during registration, the CSCF core performs the S-CSCF functionfor the originating subscriber. If topology hiding is not used nonregister messages go to the S-CSCF without going to the I-CSCF. ExternalNon none If the packet(s) are not coming from the P-CSCF networkregister interface, the packet(s) are for a destination I-CSCF/ dialogsubscriber or for proxying to another proxy. S-CSCF/ creating Demuxmanager performs a destination address BGCF/ request analysis todetermine the session manager MGCF instance handling the session. If oneis found, the packet(s) are routed to that instance. At the CSCF core,the packet(s) are checked using the learned P-CSCF address to determinethe packets are not coming from the mobile node or P-CSCF and I-CSCFfunction processing is performed. Otherwise S-CSCF function processingis performed.

From the above tables, it can be appreciated that the demux manager andthe session manager, which includes CSCF core functionalities, worktogether to direct and process packets. FIG. 5 illustrates animplementation of demux and session manager in accordance with certainembodiments. FIG. 5 includes packet accelerator card (PAC) 510, PAC 512,and PAC 514. PACs 510, 512, and 514 may also be implemented in a packetservices card (PSC) or any other applicable hardware/softwareconfiguration. PAC 510 implements a SIP demux manager 516 which includessubscriber hash list 518. SIP demux manager 516 can be used to directSIP messaging and packets to the session manager handling the sessionand to external functions. The SIP demux manager 516 can cacheinformation about a session and a subscriber in a subscriber hash list518 to reduce delay in directing packets to their corresponding sessionmanagers.

PAC 512 implements session manager 520 and 522. Session manager 520includes a CSCF core 524, a subscriber local cache 526, a call statedata 528, and a SIP stack 530. CSCF core 524 can include a P-CSCF, aS-CSCF, and a I-CSCF or can implement the functions of a P-CSCF, aS-CSCF, and/or a I-CSCF on packet(s) in session manager 520. Subscriberlocal cache 526 includes a number of pieces of information which can beused to reduce lookup times for routing packets from the session manageror reduce direction analysis processing time. For example, AOR/publicuser identity, private user identity (unique for a subscriber, could beIMSI), contact, registration expiry, registration status (active,expired), service route header/path header, auth vector, and subscriberprofile. Call state data includes information about the state ofsessions, e.g., registerted, alerting, answered, release, and wait,which can be used to make decisions on whether to allocate or deallocateresources and accept or reject messages coming from the network.

SIP stack 530 includes a connection handler (CH), a transaction manager(TM), and a user application (UAPP). The connection handler manages theconnections to remote servers over a single communications interface,and handles the formatting and multiplexing of outbound SIP messages aswell as the parsing and de-multiplexing of inbound SIP messages.Transaction manager implements the core SIP functionality and supportsproxy server, registrar, redirect server, and user agentfunctionalities. User application manages the correlators and handlesused to identify calls, sessions, and transactions in the SIP stack.

By caching information in the SIP demux manager and the session manager,these entities can make routing decisions quicker because lookup time issaved. In some embodiments, the NPU flows can direct the packet flows tothe session manager handling the session and the session manager cachecan be used for obtaining information regarding the subscriber. Thedemux manager can direct packets that are not picked up by a NPU flow orare the registration packets from a mobile node, in certain embodiments.

The session manager can act as a registrar and redirect server. Aregistrar allows the SIP user to register the contact information (IPaddress/domain name) where the SIP user can be reached. The registrarcan be a location service that allows binding between the logicaladdress/public identity of the SIP user with the physical address. A SIPproxy or redirect server can locate the user by contacting theregistrar. The registrar can be used by the S-CSCF functionality in thesession manager. The P-CSCF and I-CSCF may proxy the registrations. Ifthe session manager is implementing a S-CSCF registrar, registrar 334(FIG. 3) can contact the CSCF core to get the authentication vector andsubscriber information. The registrar can perform the SIP specificregistrar functionality, but take directions from the S-CSCF componentin CSCF core in some embodiments.

The system of FIG. 3 may maintain a local cache per service or sessionand also send updates to demux manager of any changes in theregistration status because demux manager maintains a local cache aswell, in some embodiments. The local cache can store the followinginformation: AOR/public user identity, private user identity (unique fora subscriber, could be IMSI), contact information, registration expiry,registration status (active, expired), service route header, authvector, and subscriber profile. The local cache entry may be deletedonce the subscriber deregisters and may maintain one such entry forevery public user identity for that subscriber.

In certain embodiments, information is cached locally to reduce setupdelay that is caused from retrieving information from externaldatabases. In some embodiments, when a subscriber registers for a firsttime, the location information provided in the registration message isstored in the demux manager. A process instance can be allocated forkeeping the subscribers call state and contact information. Otherinformation can also be stored. This information is used so that a callcoming to or from the demux manager is directed to the process instancehandling the session. The information can also be used to distribute thetraffic so that a bottleneck does not occur at the demux manager.

In some embodiments, a cache including information from a registrationmessage is used to distribute traffic coming in, e.g., from a publicswitched telephone network (PSTN) or a SIP interconnect. This can beimplemented by storing the IP address and a handle, such as the Addressof Record (AoR). The AoR can be a SIP handle such assip:name@starentnetworks.com orsip:phonenumber@starentnetworks.com;user=phone or a tel:phonenumberwhich is a tel URI. This handle information is generally stored inanother database and lookup can take some time. Thus, when aregistration message comes in it can use information, such as the SIPhandle and do a reverse lookup in the database and get informationincluding the telephone number to place in the cache. This databaseinformation can be used when a request comes in from PSTN with atelephone number. The telephone number can be matched against theinformation in the cache to route the traffic flow to the processinstance handling the call session.

In certain embodiments, a network processing unit (NPU) directs trafficto the process instance that handles the call session bypassing thedemux manager and the signaling routing layer (see FIG. 3). The NPU canuse a hash key to determine if the demux manager can be bypassed. Ifthere is a hash hit, the traffic is routed directly to a session managerprocess instance handling the call. In some embodiments, the processinstance is inside the call processing layer and can be within the CSCFcore. The process instance can be given an internal address so thetraffic can be directed to it. This internal address is used by the NPUto send the incoming packet(s) to the correct session manager processinstance after a hash hit.

In certain embodiments, the system of FIG. 3 caches subscriber andvarious network SIP node's presence locally and uses various networkaddresses learnt during subscriber registration to distribute futuretraffic among internal CSCF processing functions as well as externalCSCF components. This system can also get the tel URI from the ENUMdatabase for the subscriber's address of record (AoR) duringregistration process itself so that the lookup during call setup timecan be avoided in some embodiments.

FIG. 6 illustrates packet management by the gateway in certainembodiments. At 610, a message or packets are received at the gateway.If the message is a register message or includes information for a newsession, the message or packet(s) is processed and analyzed by the demuxmanager at step 612. The demux manager can cache certain informationextracted from the message to aid in routing future messages. The demuxmanager also selects a session manager for handling the message in 612.The session manager receives the message from the demux manager in 614and caches a number of fields and other information from the message.The session manager may also setup a NPU flow to direct packet flows in614. The message can then be directed to the next destination in 616.

If the message has already been assigned a session manager, the demuxmanager can use a hash list to make a number of routing decisions. In618, after a message is received at the gateway in 610, the messagematches identifying information in the demux manager's hash list. When amatch is made against the demux manager, the demux manager sends thepackets or message to the previously allocated session manager in 620.The session manager can make further determinations about how thepackets or message is to be handled and direct it to the nextdestination in 616.

If the message has already been assigned a session manager, the messagemay match against a NPU flow hast list in 622, after being received atthe gateway in 610. The NPU flow can redirect a number of common packetsor messages using a limited set of information. The NPU flow can bemostly implemented in hardware to decrease delay in routing the packets.The NPU flow can relieve the demux manager from having to inspect eachincoming packet. If a packet does not match against the NPU flow it canbe sent to the demux manager for routing. In some embodiments the NPUflow passes the packet on to the session manager handling the sessionfor further processing and/or routing in 624. The message is thendirected to the next destination in 616.

The gateway described above is implemented in a chassis in someembodiments. This chassis can implement multiple and differentintegrated functionalities. In some embodiments, an access gateway, apacket data serving node (PDSN), a foreign agent (FA), or a home agent(HA) can be implemented on a chassis. Other types of functionalities canalso be implemented on a chassis in other embodiments are a GatewayGeneral packet radio service Support Node (GGSN), a serving GPRS supportnode (SGSN), a packet data inter-working function (PDIF), an accessservice network gateway (ASNGW), a base station, a access network, aUser Plane Entity (UPE), an IP Gateway, an access gateway, a sessioninitiation protocol (SIP) server, a proxy-call session control function(P-CSCF), and an interrogating-call session control function (I-CSCF).In certain embodiments, one or more of the above-mentioned other typesof functionalities are integrated together or provided by the samefunctionality. For example, an access network can be integrated with aPDSN. A chassis can include a PDSN, a FA, a HA, a GGSN, a PDIF, anASNGW, a UPE, an IP Gateway, an access gateway, or any other applicableaccess interface device. In certain embodiments, a chassis is providedby Starent Networks, Corp. of Tewksbury, Mass. in a ST16 or a ST40multimedia platform.

The features of a chassis that implements an enterprise access gateway,in accordance with some embodiments, are further described below. Thechassis includes slots for loading application cards and line cards. Amidplane can be used in the chassis to provide intra-chassiscommunications, power connections, and transport paths between thevarious installed cards. The midplane can include buses such as a switchfabric, a control bus, a system management bus, a redundancy bus, and atime division multiplex (TDM) bus. The switch fabric is an IP-basedtransport path for user data throughout the chassis implemented byestablishing inter-card communications between application cards andline cards. The control bus interconnects the control and managementprocessors within the chassis. The chassis management bus providesmanagement of system functions such as supplying power, monitoringtemperatures, board status, data path errors, card resets, and otherfailover features. The redundancy bus provides transportation of userdata and redundancy links in the event of hardware failures. The TDM busprovides support for voice services on the system.

The chassis supports at least two types of application cards: a switchprocessor card and a packet accelerator card. The switch processor cardserves as a controller of the chassis and is responsible for such thingsas initializing the chassis and loading software configurations ontoother cards in the chassis. The packet accelerator card provides packetprocessing and forwarding capabilities. Each packet accelerator card iscapable of supporting multiple contexts. Hardware engines can bedeployed with the card to support parallel distributed processing forcompression, classification traffic scheduling, forwarding, packetfiltering, and statistics compilations.

The packet accelerator card performs packet-processing operationsthrough the use of control processors and a network processing unit(NPU). The network processing unit determines packet processingrequirements; receives and transmits user data frames to/from variousphysical interfaces; makes IP forwarding decisions; implements packetfiltering, flow insertion, deletion, and modification; performs trafficmanagement and traffic engineering; modifies/adds/strips packet headers;and manages line card ports and internal packet transportation. Thecontrol processors, also located on the packet accelerator card, providepacket-based user service processing. The line cards when loaded in thechassis provide input/output connectivity and can also provideredundancy connections as well.

In some embodiments, a ST40 embodiment of the chassis can support asystem management card (SMC) and a packet services card (PSC). Thesystem management card is a system control and management card formanaging and controlling other cards in the chassis. The packet servicescard is a high-speed processing card that provides mutli-threadedpoint-to-point, packet data processing, and context processingcapabilities, among other things.

The operating system software can be based on a Linux software kerneland run specific applications in the chassis such as monitoring tasksand providing protocol stacks. The software allows chassis resources tobe allocated separately for control and data paths. For example, certainpacket accelerator cards can be dedicated to performing routing orsecurity control functions, while other packet accelerator cards arededicated to processing user session traffic. As network requirementschange, hardware resources can be dynamically deployed to meet therequirements in some embodiments. The system can be virtualized tosupport multiple logical instances of services, such as technologyfunctions (e.g., a PDSN, ASNGW, PDIF, HA, GGSN, or IPSG).

The chassis' software can be divided into a series of tasks that performspecific functions. These tasks communicate with each other as needed toshare control and data information throughout the chassis. A task is asoftware process that performs a specific function related to systemcontrol or session processing. Three types of tasks operate within thechassis in some embodiments: critical tasks, controller tasks, andmanager tasks. The critical tasks control functions that relate to thechassis' ability to process calls such as chassis initialization, errordetection, and recovery tasks. The controller tasks mask the distributednature of the software from the user and perform tasks such as monitorthe state of subordinate manager(s), provide for intra-managercommunication within the same subsystem, and enable inter-subsystemcommunication by communicating with controller(s) belonging to othersubsystems. The manager tasks can control system resources and maintainlogical mappings between system resources.

Individual tasks that run on processors in the application cards can bedivided into subsystems. A subsystem is a software element that eitherperforms a specific task or is a culmination of multiple other tasks. Asingle subsystem can include critical tasks, controller tasks, andmanager tasks. Some of the subsystems that can run on a chassis includea system initiation task subsystem, a high availability task subsystem,a recovery control task subsystem, a shared configuration tasksubsystem, a resource management subsystem, a virtual private networksubsystem, a network processing unit subsystem, a card/slot/portsubsystem, and a session subsystem.

The system initiation task subsystem is responsible for starting a setof initial tasks at system startup and providing individual tasks asneeded. The high availability task subsystem works in conjunction withthe recovery control task subsystem to maintain the operational state ofthe chassis by monitoring the various software and hardware componentsof the chassis. Recovery control task subsystem is responsible forexecuting a recovery action for failures that occur in the chassis andreceives recovery actions from the high availability task subsystem.Shared configuration task subsystem provides the chassis with an abilityto set, retrieve, and receive notification of chassis configurationparameter changes and is responsible for storing configuration data forthe applications running within the chassis. Resource managementsubsystem is responsible for assigning resources (e.g., processor andmemory capabilities) to tasks and for monitoring the task's use of theresources.

Virtual private network (VPN) subsystem manages the administrative andoperational aspects of VPN-related entities in the chassis, whichinclude creating separate VPN contexts, starting IP services within aVPN context, managing IP pools and subscriber IP addresses, anddistributing the IP flow information within a VPN context. In someembodiments, within the chassis, IP operations are done within specificVPN contexts. The network processing unit subsystem is responsible formany of the functions listed above for the network processing unit. Thecard/slot/port subsystem is responsible for coordinating the events thatoccur relating to card activity such as discovery and configuration ofports on newly inserted cards and determining how line cards map toapplication cards. The session subsystem is responsible for processingand monitoring a mobile subscriber's data flows in some embodiments.Session processing tasks for mobile data communications include: A10/A11termination for CDMA networks, GSM tunneling protocol termination forGPRS and/or UMTS networks, asynchronous PPP processing, packetfiltering, packet scheduling, Difsery codepoint marking, statisticsgathering, IP forwarding, and AAA services, for example. Responsibilityfor each of these items can be distributed across subordinate tasks(called managers) to provide for more efficient processing and greaterredundancy. A separate session controller task serves as an integratedcontrol node to regulate and monitor the managers and to communicatewith the other active subsystem. The session subsystem also managesspecialized user data processing such as payload transformation,filtering, statistics collection, policing, and scheduling.

In some embodiments, the software needed for implementing a process or adatabase includes a high level procedural or an object-orientatedlanguage such as C, C++, C#, Java, or Perl. The software may also beimplemented in assembly language if desired. Packet processingimplemented in a chassis can include any processing determined by thecontext. For example, packet processing may involve high-level data linkcontrol (HDLC) framing, header compression, and/or encryption. Incertain embodiments, the software is stored on a storage medium ordevice such as read-only memory (ROM), programmable-read-only memory(PROM), electrically erasable programmable-read-only memory (EEPROM),flash memory, or a magnetic disk that is readable by a general orspecial purpose-processing unit to perform the processes described inthis document.

Although the present invention has been described and illustrated in theforegoing embodiments, it is understood that the present disclosure hasbeen made only by way of example, and that numerous changes in thedetails of implementation of the invention may be made without departingfrom the spirit and scope of the invention, which is limited only by theclaims which follow.

1.-20. (canceled)
 21. A method: receiving a plurality of packets at agateway; in response to a determination that a first packet matches oneor more criteria of a set of criteria, forwarding the packet to a firstprocess instance of one or more process instances of the gateway, thefirst process instance corresponding to the one or more criteria; and inresponse to a determination that a second packet does not match anycriteria of the set of criteria, determining whether to add a secondprocess instance to handle a new packet flow associated with the secondpacket based at least on load information of the first process instance.22. The method of claim 21, further comprising sending from the firstprocess instance a limited set of criteria to set up a flow in a networkprocessing unit to forward packets that match the limited set ofcriteria.
 23. The method of claim 21, wherein the one or more criteriacomprises an originating subscriber address.
 24. The method of claim 21,wherein the one or more criteria comprises a destination subscriberaddress.
 25. The method of claim 21, wherein the determination that thefirst packet matches one or more criteria of the set of criteriacomprises checking an originating subscriber address and subsequentlychecking a destination subscriber address.
 26. The method of claim 21,wherein the determination that the first packet matches one or morecriteria of the set of criteria comprises comparing information obtainedfrom the first packet with at least a portion of a hash list.
 27. Themethod of claim 21, wherein the first process instance comprises atleast a portion of a call session control function (CSCF).
 28. Themethod of claim 21, wherein each process instance comprises aProxy-CSCF, an Interrogating CSCF, and a Serving CSCF.
 29. The method ofclaim 21, further comprising selecting a process instance of the one ormore process instances for a packet flow based on a load of one or moreof the one or more process instances.
 30. At least one non-transitorymedia comprising logic that when executed is operable to: in response toa determination that a first packet matches one or more criteria of aset of criteria, forward the packet to a first process instance of oneor more process instances of a gateway, the first process instancecorresponding to the one or more criteria; and in response to adetermination that a second packet does not match any criteria of theset of criteria, determine whether to add a second process instance tohandle a new packet flow associated with the second packet based atleast on load information of the first process instance.
 31. The atleast one media of claim 30, wherein the logic when executed is furtheroperable to send from the first process instance a limited set ofcriteria to set up a flow in a network processing unit to forwardpackets that match the limited set of criteria.
 32. The at least onemedia of claim 30, wherein the one or more criteria comprises anoriginating subscriber address.
 33. The at least one media of claim 30,wherein the one or more criteria comprises a destination subscriberaddress.
 34. The at least one media of claim 30, wherein thedetermination that the first packet matches one or more criteria of theset of criteria comprises checking an originating subscriber address andsubsequently checking a destination subscriber address.
 35. The at leastone media of claim 30, wherein the determination that the first packetmatches one or more criteria of the set of criteria comprises comparinginformation obtained from the first packet with at least a portion of ahash list.
 36. The at least one media of claim 30, wherein the firstprocess instance comprises at least a portion of a call session controlfunction (CSCF).
 37. The at least one media of claim 30, wherein eachprocess instance comprises a Proxy-CSCF, an Interrogating CSCF, and aServing CSCF.
 38. The at least one media of claim 30, wherein the logicwhen executed is further operable to select a process instance of theone or more process instances for a packet flow based on a load of oneor more of the one or more process instances.